Skip to content

Update RFC5646 data#8

Merged
ptr727 merged 2 commits into
mainfrom
develop
Jun 30, 2025
Merged

Update RFC5646 data#8
ptr727 merged 2 commits into
mainfrom
develop

Conversation

@ptr727

@ptr727 ptr727 commented Jun 30, 2025

Copy link
Copy Markdown
Owner

No description provided.

Copilot AI review requested due to automatic review settings June 30, 2025 03:03

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR updates the RFC5646 data set and related tooling to include a new “viennese” variant and bumps the file date, while also refining code patterns and documentation formatting.

  • Standardize example bullet formatting in README and remove trailing backslashes
  • Switch to await using in HTTP download to ensure async disposal
  • Bump generated data date and add the "viennese" variant in code, JSON, and registry file
  • Introduce normalization TODOs in lookup methods

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

Show a summary per file
File Description
README.md Unified list markers and stripped escape backslashes
LanguageTagsCreate/Program.cs Updated to await using for httpStream disposal
LanguageTags/rfc5646DataGen.cs Updated FileDate and inserted new “viennese” entry
LanguageTags/LanguageLookup.cs Added TODOs to parse/normalize input before matching
LanguageData/rfc5646.json Updated FileDate and added new “viennese” record
LanguageData/rfc5646 Updated File-Date and appended “viennese” variant block
Comments suppressed due to low confidence (3)

README.md:169

  • The list markers and removal of trailing backslashes may affect Markdown rendering. Consider using a consistent single-hyphen plus space (- ) for bullets and ensure that line breaks render as intended.
- `pt` will match `pt` Portuguese, or `pt-BR` Brazilian Portuguese, or `pt-PT` European Portuguese.

LanguageTags/LanguageLookup.cs:119

  • This TODO appears twice in separate methods. You may want to extract the parsing and normalization logic into a shared helper to avoid duplication and keep the code DRY.
        // TODO: Conditional parse and normalize before processing

@ptr727 ptr727 merged commit 4e8a388 into main Jun 30, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants